home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.cs.arizona.edu
/
ftp.cs.arizona.edu.tar
/
ftp.cs.arizona.edu
/
icon
/
newsgrp
/
group98c.txt
/
000015_icon-group-sender _Fri Sep 11 13:08:35 1998.msg
< prev
next >
Wrap
Internet Message Format
|
2000-09-20
|
1KB
Return-Path: <icon-group-sender>
Received: from kingfisher.CS.Arizona.EDU (kingfisher.CS.Arizona.EDU [192.12.69.239])
by baskerville.CS.Arizona.EDU (8.9.1a/8.9.1) with SMTP id NAA07439
for <icon-group-addresses@baskerville.CS.Arizona.EDU>; Fri, 11 Sep 1998 13:08:35 -0700 (MST)
Received: by kingfisher.CS.Arizona.EDU (5.65v4.0/1.1.8.2/08Nov94-0446PM)
id AA31741; Fri, 11 Sep 1998 13:08:08 -0700
Message-Id: <4FD6422BE942D111908D00805F3158DF0757B57E@RED-MSG-52>
From: Todd Proebsting <toddpro@microsoft.com>
To: icon-group@optima.CS.Arizona.EDU
Subject: RE: Unicode support or support for non-ASCII based character ma
Date: Fri, 11 Sep 1998 08:44:01 -0700
X-Mailer: Internet Mail Service (5.5.2232.9)
Errors-To: icon-group-errors@optima.CS.Arizona.EDU
Status: RO
Jcon (http://www.cs.arizona.edu/icon/jcon) originally used Java's Unicode
strings as the basis for implementing Icon strings. This was trivial to do,
and we (Gregg Townsend and I) would have kept that implementation except
that it was much too slow. I blame this in large part on the Java "String"
implementation, and not on Unicode. (Although Unicode obviously wastes a
lot of space in applications that are just using the ASCII subset.)
Prior to switching to ASCII, we never faced the problem of what was the
"right" thing to do with pre-defined csets with Unicode. For instance, what
are the elements of the cset &ucase in an Unicode world?
Todd Proebsting